v1.4.1

Compare Source

   🐞 Bug Fixes

• Add node: prefix to build-in modules  -  by @​danielroe in https://github.com/nuxt/eslint/issues/579 (8180f)
• Sort imports objects by from + name  -  by @​danielroe in https://github.com/nuxt/eslint/issues/578 (766ae)

    View changes on GitHub

v1.4.0

Compare Source

   🚀 Features

• Update deps  -  by @​antfu (afc42)
• Support type-aware rules, fix #​499  -  by @​antfu in https://github.com/nuxt/eslint/issues/499 (70d23)

    View changes on GitHub

v9.27.0

Compare Source

v3.1.4

Compare Source

v4.16.1

Compare Source

Patch Changes

• #​9268 7344344 Thanks @​gabivlj! - wrangler containers delete handles API errors correctly

v4.16.0

Compare Source

Minor Changes

• #​9288 3b8f7f1 Thanks @​petebacondarwin! - allow --name and --env args on wrangler deploy

  Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
  Now specifying --name is supported and will override any names set in the Wrangler config:

  wrangler.json

  {
  	"name": "config-worker"
  	"env": {
  		"staging": { "name": "config-worker-env" }
  	}
  }

  Command	Previous (Worker name)	Proposed (Worker name)	Comment
  wrangler deploy --name=args-worker	"args-worker"	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=staging	Error	"args-worker"	CLI arg used
  wrangler deploy --name=args-worker --env=prod	Error	"args-worker"	CLI arg used
  wrangler deploy	"config-worker"	"config-worker"	Top-level config used
  wrangler deploy --env=staging	"config-worker-env"	"config-worker-env"	Named env config used
  wrangler deploy --env=prod	"config-worker-prod"	"config-worker-prod"	CLI arg and top-level config combined

• #​9265 16de0d5 Thanks @​edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

• #​9234 2fe6219 Thanks @​emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch

• #​9269 66d975e Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #​9151 5ab035d Thanks @​gabivlj! - wrangler containers can be configured with the kind of application rollout on apply

• #​9231 02d40ed Thanks @​dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

  Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

  Also include the ai binding since the bindings is already remote by default anyways.

• #​9221 2ef31a9 Thanks @​vicb! - bump @cloudflare/unenv-preset

• #​9277 db5ea8f Thanks @​penalosa! - Support Mixed Mode for more binding types

• #​9266 f2a16f1 Thanks @​petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules

• #​9245 b87b472 Thanks @​penalosa! - Support Mixed Mode Dispatch Namespaces

• Updated dependencies [db5ea8f, b87b472]:

  • [email protected]